Method and apparatus for ip/mpls fast reroute

ABSTRACT

A method is disclosed that is implemented by a router for executing an internet protocol fast reroute process in response to a network event invalidating a current route to a destination node without degrading forwarding plane functionality or performance caused by indirect forwarding information base lookups. The method comprises a set steps including receiving or generating the network event by the router, the network event associated with a network event identifier and looking up the network event identifier in an event table to determine routes that are affected by the network event. The method further includes determining whether a route with a fast reroute forwarding object is affected by the network event in the routing information base and overwriting a current next hop forwarding object using a backup next hop forwarding object in the forwarding information base.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims priority from U.S. Provisional PatentApplication No. 61/784,361, filed on Mar. 14, 2013.

FIELD OF THE INVENTION

The embodiments of the invention relate to the field of network routing.Specifically, the embodiments relate to a method and system for quicklyrerouting data traffic in response to a failure of a primary route, byswitching to a predetermined alternate route.

BACKGROUND

Internet Protocol (IP) traffic can be routed across the Internet byusing discovery and routing protocols that are executed by the nodes ofthe Internet such that they can determine optimal and loop free routesfrom any data traffic source to any data traffic destination usingtopology information exchanged between the nodes. Each node in thenetwork utilizes the topology ascertained through the discoveryprotocols to construct forwarding tables that are consistent across thenetwork. The process of arriving at these routes and forwarding tablescan be called ‘convergence.’ The routes and forwarding tables arerecalculated when there is a change in network topology. However,re-calculating these routes and tables can take time (i.e., longconvergence time) during which some traffic may be blocked or lost.

IP and Multi-Protocol Label Switching (MPLS) Fast Reroute technologiesaddress the problem with the long convergence of routing protocols byproviding backup paths, which are used when network failures occur.These technologies are important due to the increased use of IPtransport for real time services such as video, voice and television andthe increasing number of web services which all are expected to workwithout disruption.

The standard approach used in existing technologies, such as openshortest path first (OSPF)/intermediate system-intermediate system(ISIS)/link discovery protocol (LDP) loop free alternative (LFA),maximally redundant trees (MRT), border gateway protocol (BGP) fastreroute (FRR), is to gather network information using arouting/signaling protocol and based on that information compute thebackup paths necessary to prepare for failures of adjacent links ornodes, and then to pre-provision the forwarding plane with those back-uppaths. The forwarding plane is then able to react on a failure event andswitch from a primary path to a back-up path without waiting for therouting protocol to gather updated network information and converge.

SUMMARY

A method is disclosed that is implemented by a router for executing aninternet protocol fast reroute process in response to a network eventinvalidating a current route to a destination node without degradingforwarding plane functionality or performance caused by indirectforwarding information base lookups. The method comprises a set stepsincluding receiving or generating the network event by the router, thenetwork event associated with a network event identifier and looking upthe network event identifier in an event table to determine routes thatare affected by the network event. The method further includesdetermining whether a route with a fast reroute forwarding object isaffected by the network event in the routing information base andoverwriting a current next hop forwarding object using a backup next hopforwarding object in the forwarding information base.

A network element is disclosed for executing an internet protocol fastreroute process in response to a network event invalidating a currentroute to a destination node without degrading forwarding planefunctionality or performance caused by indirect forwarding informationbase lookups. The network element comprising a first storage device tostore a routing information base and a line card including a networkprocessing device and a storage device, the storage device to store theforwarding information base. The network processor is configured toexecute a proxy function module and a switch function module. The proxyfunction module is configured to receive or generate the network event,the network event associated with a network event identifier, to look upthe network event identifier in an event table to determine routes thatare affected by the network event, and to determine whether a route witha fast reroute forwarding object is affected by the network event in therouting information base. The switch function module is configured tooverwrite a current next hop forwarding object using a backup next hopforwarding object in the forwarding information base.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings in which likereferences indicate similar elements. It should be noted that differentreferences to “an” or “one” embodiment in this disclosure are notnecessarily to the same embodiment, and such references mean at leastone. Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to effect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described.

FIG. 1A is a flowchart of one embodiment of a process for implementing afast reroute process using fast reroute routing information baseforwarding objects.

FIG. 1B is a flowchart of one embodiment of a process for implementing afast reroute process using hierarchical fast reroute routing informationbase forwarding objects.

FIG. 2A is a diagram of one embodiment of an example topology and routerconfiguration using fast reroute routing information base forwardingobjects.

FIG. 2B is a diagram of one embodiment of an example topology and routerconfiguration using hierarchical fast reroute routing information baseforwarding objects.

FIG. 3A is a diagram of one example embodiment of a network elementimplementing a fast reroute process using fast reroute routerinformation base forwarding objects.

FIG. 3B is a diagram of one example embodiment of a network elementimplementing a fast reroute process using fast reroute routerinformation base forwarding objects.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth.However, it is understood that embodiments of the invention may bepracticed without these specific details. In other instances, well-knowncircuits, structures and techniques have not been shown in detail inorder not to obscure the understanding of this description. In otherinstances, control structures, gate level circuits and full softwareinstruction sequences have not been shown in detail in order not toobscure the invention. Those of ordinary skill in the art, with theincluded descriptions, will be able to implement appropriatefunctionality without undue experimentation.

In the following description and claims, the terms “coupled” and“connected,” along with their derivatives, may be used. It should beunderstood that these terms are not intended as synonyms for each other.“Coupled” is used to indicate that two or more elements, which may ormay not be in direct physical or electrical contact with each other,co-operate or interact with each other. “Connected” is used to indicatethe establishment of communication between two or more elements that arecoupled with each other.

To facilitate understanding of the embodiments, dashed lines have beenused in the figures to signify the optional nature of certain items(e.g., features not supported by a given embodiment of the invention;features supported by a given embodiment, but used in some situationsand not in others).

The techniques shown in the figures can be implemented using code anddata stored and executed on one or more electronic devices. Anelectronic device (e.g., an end station, a network device) stores andtransmits (internally and/or with other electronic devices over anetwork) code (composed of software instructions) and data usingmachine-readable media, such as non-transitory machine-readable media(e.g., machine-readable storage media such as magnetic disks; opticaldisks; read only memory; flash memory devices; phase change memory) andtransitory machine-readable transmission media (e.g., electrical,optical, acoustical or other form of propagated signals—such as carrierwaves, infrared signals). In addition, such electronic devices includeshardware such as a set of one or more processors coupled to one or moreother components, such as one or more non-transitory machine-readablemedia (to store code and/or data), user input/output devices (e.g., akeyboard, a touchscreen, and/or a display), and network connections (totransmit code and/or data using propagating signals). A ‘set,’ as usedherein, refers to any positive whole number of items. The coupling ofthe set of processors and other components is typically through one ormore busses and bridges (also termed as bus controllers). Thus, anon-transitory machine-readable medium of a given electronic devicetypically stores instructions for execution on one or more processors ofthat electronic device. One or more parts of an embodiment of theinvention may be implemented using different combinations of software,firmware, and/or hardware.

As used herein, a network device (e.g., a router, switch, bridge) is apiece of networking equipment, including hardware and software thatcommunicatively interconnects other equipment on the network (e.g.,other network devices, end stations). Some network devices are “multipleservices network devices” that provide support for multiple networkingfunctions (e.g., routing, bridging, switching, Layer 2 aggregation,session border control, Quality of Service, and/or subscribermanagement), and/or provide support for multiple application services(e.g., data, voice, and video). Subscriber end stations (e.g., servers,workstations, laptops, netbooks, palm tops, mobile phones, smartphones,multimedia phones, Voice Over Internet Protocol (VOIP) phones, userequipment, terminals, portable media players, GPS units, gaming systems,set-top boxes) access content/services provided over the Internet and/orcontent/services provided on virtual private networks (VPNs) overlaid on(e.g., tunneled through) the Internet. The content and/or services aretypically provided by one or more end stations (e.g., server endstations) belonging to a service or content provider or end stationsparticipating in a peer to peer service, and may include, for example,public webpages (e.g., free content, store fronts, search services),private webpages (e.g., username/password accessed webpages providingemail services), and/or corporate networks over VPNs. Typically,subscriber end stations are coupled (e.g., through customer premiseequipment coupled to an access network (wired or wirelessly)) to edgenetwork devices, which are coupled (e.g., through one or more corenetwork devices) to other edge network devices, which are coupled toother end stations (e.g., server end stations).

The embodiments of the invention described herein below provide a methodand apparatus for implementing fast reroute for Internet Protocol (IP)and multi-protocol label switching (MPLS), media access control (MAC)routes or other addressing scheme used for communication in a datanetwork. The method and apparatus implement the fast reroute withoutforwarding degradation (increased overhead or processing in theforwarding plane) by using a replica of the primary or backup next-hopforwarding information base forwarding object, which makes it possiblefor some routes to use a backup path while other routes do not. Themethod and apparatus enable many routes to point to the same fastreroute forwarding object as the next-hop, both in the control plane andin forwarding plane. The method and apparatus switch between a primaryor backup next hop by use of one single rewrite of the next-hop in theforwarding plane, which enables all routes using the backup next-hop toswitch. The method and apparatus support a control plane that keeps fullhierarchical forwarding paths for both primary and back-up routes.

Some key properties of the embodiments include that in the control planefunction a fast reroute (FRR) next-hop provides a protected (backup)path with a primary next hop and backup next-hop. In the forwardingplane function, a non-hierarchical FRR next-hop is at any instant intime a replica either of the primary next hop forwarding object or ofthe backup next-hop forwarding object. In this way, the forwarding planefunction can be totally unaware of the FRR function and therebyforwarding degradation is avoided.

The disadvantages of the prior art include that fast reroute requiresadditional processing and resources due to the use of indirection in therouting information base and forwarding information base. Also,hierarchical fast reroute without forwarding degradation is notsupported.

Fast rerouting (FRR) technologies include Loop Free Alternates (LFA) andremote LFAs, which are technologies used to provide Internet ProtocolFast rerouting (IPFRR) based on Interior Gateway Protocols (IGPs) suchas open shortest path first (OSPF) and intermediate system—intermediatesystem (ISIS) protocols. An IGP running within a router builds adatabase which tracks all links within the applicable network area. LFAcomputes loop free alternate routes using the IGP data base. Bordergateway protocol (BGP) diverse path, BGP best external, and BGP add pathare BGP technologies which gives BGP routers the capability todistribute and learn multiple alternates for a single prefix and theability to realize IPFRR. Maximally Redundant Trees (MRT) is anotherIPFRR technology which is based on knowledge of the topology of anetwork provided by an IGP. The embodiments described herein are eachcompatible with these technologies. Examples may be discussed usingspecific routing and FRR technologies, however, one skilled in the artwould understand that the principles, steps and structures of theseexamples are applicable to the other technologies.

Overview

In one embodiment, the FRR functions may be conceived of as beingpartitioned in the following four functions (1) the control planefunction, (2) the forwarding plane function, (3) the FRR proxy functionand (4) the switching function. The control plane function manages therouting/forwarding information including the routes having protectednext-hops with primary and backup next-hops defined. The control planeparticipates in routing and signaling protocols to build the routinginformation base (RIB) or similar data structure. The control plane alsoperforms the updating of the forwarding information base (FIB) for theforwarding plane.

The forwarding plane function implements the forwarding of data trafficbased on the FIB. The forwarding plane is not aware of the FRRfunctions. The FRR proxy function is an intermediary function betweenthe control plane and the forwarding plane. Towards the control plane itacts as the forwarding plane and towards the forwarding plane it acts asthe control plane. The FRR proxy function may be physically co-locatedwith the forwarding processing unit (i.e., a central processing unit ornetwork processing unit) or with the control plane processor unit (i.e.,a central processing unit) or in a separate processing unit. For routeswithout FRR next-hops the FRR proxy function simply relays the routesand next-hops to the forwarding plane. For a route with an FRR next-hop,the FRR proxy function will replace the FRR next-hop by a replica of theprimary next-hop referenced by the former. In addition, the FRR proxyfunction will relay the backup next-hop and the trigger event identitiesto the switching function to enable the switching function to performthe FRR switch-over by overwriting the FRR next-hop, i.e. overwritingthe replica of the primary next-hop with the backup next-hop informationwhen applicable events are identified.

In the case of hierarchical FRR where one FRR next-hop referencesanother FRR next-hop, the FRR proxy function compresses a chain ofmultiple FRR next-hops into a single FRR next-hop by walking thenext-hop chain through primary next-hop references until a non-FRRnext-hop is reached. The FRR proxy function provides the FRR next-hop asa replica of this first non-FRR next-hop. As in the non-hierarchicalcase, the backup and trigger identities are provided to the switchingfunction. However, in the hierarchical FRR case there may be multiplebackups where each backup is triggered by a separate event. This isillustrated by a use case with BGP FRR combined hierarchically with LDPFRR, which is discussed further herein below. The set of backupnext-hops is determined by walking the next-hop chain along the primaryreference with the exception of one level where the backup next-hop andtrigger identity is taken. Thus, for a hierarchy of n levels of FRRthere will be n backups, one for each level. The FRR proxy function alsotakes care of updating hierarchical FRR next-hops dependent on other FRRnext-hops in the next-hop chain in case of changes in the latter.

The FRR switching function as described above is responsible forperforming the FRR switchover. As with the FRR proxy function, theswitching function can be collocated with the forwarding plane, or withthe control plane, or in a separate processing unit. The switchover isimplemented by the overwriting of the FIB next hop forwarding object asspecified by the proxy function. In other embodiments, the proxy andswitching functions, can be combined or separately implemented with anycombination or permutation of functions.

FIG. 1A is a flowchart of one embodiment of a process for implementing afast reroute process using fast reroute routing information baseforwarding objects. In one embodiment, the process is executed by theproxy function and/or switch functions of the router. These functionscan be implemented at the control and forwarding planes, specificallythe processing units of these planes, which may be part of a generalrouter central processing or network processing unit (e.g., for thecontrol plane) or a central processing unit or network processing unitof a set of line cards within the router. A ‘set,’ as used herein refersto any positive whole number of items, including one item.

The process can be initiated in response to receiving a network event(Block 101). The network event can be received from an external sourcesuch as a message from a neighboring router or from an internal sourcesuch as a signal from a port or similar source. The network event can bean indicator of a change in the functioning of the router, such as afailed port, or a change in the function of the network such as a failedlink. The network event can include an event identifier that canindicate a type of the network event. Any type of encoding of thesenetwork events can be utilized and the router can look up the type ofthe event using the event identifier (Block 103). In one embodiment, anevent table can be maintained by the control plane of the router, whichcontains a set of entries identifying the actions to be taken inresponse to receiving each of the types of network events ornotifications containing the network event identifiers. In one exampleembodiment, the network event can be a fast reroute message expresslyidentifying a route to be switched to a backup route.

In one embodiment, the network event indicates that a topology of thenetwork has changed such that the routes defined in the routinginformation base of the router are affected. Each of the affected routesis checked to determine whether a fast reroute forwarding object isincluded (Block 105). The entries in the routing information base aredata structures containing information about a route from the router toa destination. This information can include next hop information andsimilar information that enables all data traffic that arrives at therouter to be forwarded toward its destination. The routing informationbase is used to manage and update a forwarding information base utilizedby the data plane of the router, which includes similar data structuresthat include next hop information for each known destination. Theseentries are described herein as being ‘objects,’ however, one skilled inthe art would understand that any type of data structure can be used torepresent and organize this information. Further, the objects form a setof information utilized for forwarding and thus, the term forwardingobject is utilized herein.

A fast reroute forwarding object is a forwarding object that can containalternate route information. The fast reroute forwarding object caninclude information including next hop information for any number ofalternate routes and related alternate route information. The next hopinformation can include an address (e.g., an IP address, port, label orsimilar address) and related information about an adjacent networkdevice such as a router. The identification and construction of thealternate routes can be accomplished using any type of routing protocoland/or protection protocol. The next hop information can be referred toas next hop forwarding objects.

Dependent of the type of network event identifier, a determination ismade whether a primary route for each destination with a fast rerouteforwarding object is no longer valid, due to a link failure, portfailure or similar problem associated with the primary route. If theprimary route is no longer valid, optionally a check may be made whetherthe backup route is valid (if the backup route is not valid then theprocess may end and require that the routing protocol reconverge). Ifthe backup route is valid, then the current next hop forwarding objectfor the destination in the forwarding information base of the forwardingplane is overwritten with a copy or replica of a next hop forwardingobject of the backup up next hop as defined in the fast rerouteforwarding object of the routing information base (Block 107). Theforwarding plane is not involved in this process at the time of datapacket forwarding. The next hop object overwrite process or ‘switch’process is transparent to the data forwarding process, which looks updestination addresses of incoming data traffic and receives differentnext hop information from a lookup in the forwarding information basebefore and after the switch.

The use of the fast reroute forwarding objects in the routinginformation base and the implementation of the FRR switch and FRR proxyfunction separate from the forwarding functions provides a fast rerouteimplementation without degradation of the forwarding function due to theforwarding function having to perform indirect next hop look ups on theforwarding information base where pointers might have been utilized inthe forwarding information base to identify backup up next hop objects.

In one embodiment, the next hop forwarding objects overwritten into theforwarding information base by the FRR switch or FRR proxy function, arereplicas or copies having unique identifiers to enable the original tobe distinguished from the copies.

The example process illustrated and described in relation to FIG. 1Ainvolves the case where there is a primary route and a backup route.However, one skilled in the art would understand that the fast rerouteforwarding object can define any number of alternate paths and/or nexthops. These alternative paths can be ranked or similarly organized suchthat the invalidity of the primary path and any number of backup pathscan be resolved to select one of the remaining valid backup paths.

In the illustrated and described embodiment of FIG. 1A, the primaryroute is overwritten with a backup or similar alternate route. However,the process can also be applied to reverse this process by overwritingthe backup with the primary route or another alternate route. Forexample, in situations where there is only a momentary fluctuation inthe availability of a link that may be a failure or only an error inreporting. In these cases, the routing protocols may not have hadsufficient time to reach convergence and the fast reroute process canquickly correct the route selection before convergence.

FIG. 1B is a flowchart of one embodiment of a process for implementing afast reroute process using hierarchical fast reroute routing informationbase forwarding objects. In one embodiment, the process is executed bythe FRR proxy function and/or FRR switch functions of the router. Thesefunctions can be implemented at the control and forwarding planes,specifically the processing units of these planes, which may be part ofa general router central processing or network processing unit (e.g.,for the control plane) or a central processing unit or networkprocessing unit of a set of line cards within the router. As discussedabove in the overview, hierarchical fast rerouting utilizes ahierarchical fast reroute object that is prepared before receipt of anetwork event. The hierarchical fast reroute object is generated bytraversing a chain of one or more non-hierarchical fast reroute objectsand compressing a primary next hop and one or more backup next-hops intoa hierarchical fast reroute object, where each backup next hop isassociated with a different network event. The hierarchical fast rerouteobjects can be generated at the time the routing information base ispopulated, in response to changes in network topology or byadministrative direction.

The process can be initiated in response to receiving a network event(Block 151). The network event can be received from an external sourcesuch as a message from a neighboring router or from an internal sourcesuch as a signal from a port or similar source. The network event can bean indicator of a change in the functioning of the router, such as afailed port, or a change in the function of the network such as a failedlink. The network event can include an event identifier that canindicate a type of the network event. Any type of encoding of thesenetwork events can be utilized and the router can look up the type ofthe event using the event identifier (Block 153). In one embodiment, anevent table can be maintained by the control plane of the router, whichcontains a set of entries identifying the actions to be taken inresponse to receiving each of the types of network events ornotifications containing the network event identifiers. The event tablecan be distributed by the control plane to the switching functionlocated in close proximity to the forwarding process. In one exampleembodiment, the network event can be a fast reroute message expresslyidentifying a route to be switched to a backup route.

In one embodiment, the network event indicates that a topology of thenetwork has changed such that the routes defined in the routinginformation base of the router are affected. Each of the affected routesis checked to determine whether hierarchical fast reroute forwardingobjects are included (Block 155). A ‘hierarchical fast reroute’forwarding object is a forwarding object that can contain alternateroute information that encompasses multiple protocols or network levels.The hierarchical fast reroute forwarding object can include informationincluding next hop information for any number of alternate routes andnetwork levels or protocols and related alternate route information. Thenext hop information for each network level can include an address(e.g., an IP address, port, label or similar address) and relatedinformation about an adjacent network device such as a router or anetwork edge device depending on the network level of the forwardingobject. The identification and construction of the alternate routes canbe accomplished using any type or combination of routing protocolsand/or protection protocols.

Dependent of the type of network event identifier, a determination ismade whether a primary route for each destination with hierarchical fastreroute forwarding objects is no longer valid, due to a link failure,port failure or similar problem associated with the primary route. Ifthe primary route is no longer valid, then a check may be made whetherthe backup route is valid (if the backup route is not valid then theprocess may end and require that the routing protocol reconverge). Ifthe backup route is valid, then the current next hop forwarding objectfor the destination in the forwarding information base of the forwardingplane is overwritten with a copy or replica of a next hop forwardingobject of the backup up next hop as defined in the hierarchical fastreroute forwarding object of the routing information base (Block 157).

Just as with the non-hierarchical case, the forwarding plane is notinvolved in this process at the time of data packet forwarding. The nexthop object overwrite process or ‘switch’ process is transparent to thedata forwarding process, which looks up destination addresses ofincoming data traffic and receives different next hop information from alookup in the forwarding information base before and after the switch.

The use of the hierarchical fast reroute forwarding objects in therouting information base and the implementation of the FRR switch andFRR proxy function separate from the forwarding functions provides afast reroute implementation without degradation of the forwardingfunction due to the forwarding function having to perform indirect nexthop look ups on the forwarding information base where pointers mighthave been utilized in the forwarding information base to identify backupup next hop objects. Standard forwarding information bases and routinginformation bases are not capable of supporting hierarchical fastreroute processes without forwarding degradation.

In one embodiment, as with the non-hierarchical process, the next hopforwarding objects overwritten into the forwarding information base bythe switch or proxy function are replicas or copies having uniqueidentifiers to enable the original to be distinguished from the copies.

The example illustrated and described in relation to FIG. 1B involvesthe case where there is a primary route and a backup route. However, oneskilled in the art would understand that the hierarchical fast rerouteforwarding object can define any number of alternate paths and/or nexthops at each network level. These alternative paths can be ranked orsimilarly organized such that the invalidity of the primary path and anynumber of backup paths can be resolved to select one of the remainingvalid backup paths.

FIG. 2A is a diagram of one embodiment of an example topology and routerconfiguration using fast reroute routing information base forwardingobjects. A network topology 201 is shown with four nodes in a simplifiedexample to illustrate the operation of a non-hierarchical fast rerouteprocess using fast reroute forwarding objects. The network topology 201includes a source node ‘S’, two intermediate nodes ‘N’ and ‘N1’ and adestination node. The source node here refers to the node at which thedata traffic is currently being processed enroute to the destinationnode through one of two alternate routes via N or N1.

The other information illustrated is the configuration of the differentfunctions separated into a control plane 203 and a forwarding plane 205of the source node. The FIB 207 includes a current next hop object thatidentifies N 209, which is part of the primary path from S to D. Thecontrol plane 203, more specifically, the routing information base 211,includes the illustrated forwarding object including a destinationaddress or destination address prefix (e.g., 3.1.1.0/24), the fastreroute next hop options for fast reroute (e.g., pointers to the nexthop forwarding objects of 1.1.1.1 and 2.1.1.1), which point to theoriginal next hop forwarding objects. The switch function 215 is shownoverwriting a replica next hop forwarding object 217 in response to anetwork event trigger 219 to the forwarding plane, specifically to theforwarding information base 207 of the forwarding plane. The ‘before’and ‘after’ views of the forwarding plane are shown with the forwardinginformation base 207 having the next hop forwarding object replica ofthe primary route next hop assigned to the destination address in the‘before’ the switch case. The ‘after’ the switch case has the replicanext hop forwarding object assigned to the same destination address inthe forwarding information base 207.

FIG. 2B is a diagram of one embodiment of an example topology and routerconfiguration using hierarchical fast reroute routing information baseforwarding objects. Similar to the non-hierarchical example diagram,this diagram shows a simplified network for sake of illustration. Thisexample network 251 includes a source node S, a destination node D1, twointermediate nodes N1 and N2, and two provider edge nodes PE1 and PE2.In this example network topology, the nodes from S to each PE are withina first network domain and routing is implemented via multi-protocollabel switching (MPLS). At each PE the routing transitions to anothernetwork to reach D1, this routing is managed by BGP. Thus, there aremultiple network levels to be managed in this example. Each networklevel can have multiple routes. In this example, there are threealternate MPLS routes (i.e., label switched paths (LSPs) determinedusing the link discovery protocol (LDP), labeled L11, L12 and L22, whichtraverse the MPLS network between the source and PEs. From the two PEsthere are two paths to the destination D1 labeled v1 and v2.

As with the non-hierarchical configuration, the FIB 253 contains a setof next hop objects. The control plane 255 includes an entry for thedestination D1 in the routing information base 257 where there is ahierarchical fast reroute forwarding object 259 including two BGP levelentries and one LDP fast reroute forwarding object 261. The BGP fastreroute forwarding object 259 includes pointers or references to nexthop forwarding objects for reaching PE1 and PE2. Each of these next hopforwarding objects is tied to forwarding objects for reaching therespective PE via MPLS. The PE1 is reachable via LSP 11 and LSP 12, andthe second level forwarding objects 261 include pointers to the next hopforwarding objects for LSP 11 and LSP 12. The PE2 is reachable only viaa single LSP 22, and the second level forwarding object points to thenext hop forwarding object of LSP 22.

The FRR switch function 263 is shown to demonstrate the possibletriggers leading to the overwriting of the next hop forwarding object ofthe primary path in the FIB 253 of the forwarding plane 265, which is areplica of LSP 11, with the replica of LSP22 or LSP 12 depending on thetrigger. A two level hierarchical network is shown that uses BGP andLDP, however, one skilled in the art would understand that the networkcan have any number of additional layers and routes consistent with theprinciples, processes and structures discussed in relation to the twolevel example and the processes discussed herein above.

FIG. 3A is a diagram of one example embodiment of a network elementimplementing a fast reroute process using fast reroute routerinformation base forwarding objects. This figure is an abstraction ofthe implementation showing the relationship between the control plane301 and the forwarding plane 303. The control plane includes the routinginformation base (RIB) 305, which is maintained by the routing ordiscovery protocols 307 that communicate with adjacent routers todetermine the network topology.

The control plane 301 provides the IP FRR proxy 309 (encompassing theproxy and switching functions described herein above) with the RIBinformation and network event information necessary for it to performthe switch from a primary route to a backup (or other alternate) routeby reconfiguring the forwarding plane 303 (i.e., updating/overwritingthe forwarding information base 311) immediately, rather than waitingfor convergence of the discovery or routing protocols to update theforwarding information of the RIB and subsequently the FIB 311.

Data can in this manner be continuously forwarded by the forwardingplane 303 without degradation of its function though the overhead ofindirect FIB lookups or similar operations that require additionalresources of the forwarding plane 303. The abstracted illustration canbe implemented in discrete hardware within a single router as describedherein below. The abstraction applies to embodiments with eitherhierarchical or non-hierarchical fast reroute forwarding objects.

FIG. 3B is a diagram of one example embodiment of a network elementimplementing a fast reroute process using fast reroute routerinformation base forwarding objects. In one embodiment, the router 350includes a set of line cards 351A, B, a switch fabric 353, and a centralprocessing unit 355A, B. The line cards 351A,B are primarily responsiblefor implementing the forwarding plane including the forwarding ofreceived data traffic toward a destination node. The central processingunit 355A, B is primarily responsible for implementing the control planeincluding managing a routing information base (RIB) 357. The switchfabric 353 facilitates the communication of data traffic between linecards 351A, B.

The line cards 351A, B can include a set of network processing units 359and/or a central processing unit 355A, B. The network processing unit(NPU) 359 can be any type of processor configured to execute datatraffic and forwarding functions via a forwarding function module 375including possibly multiple levels of processing of received datatraffic. The NPU 359 can include or be in communication with aforwarding information base (FIB) 361 with next hop information for eachdestination address or destination prefix. The FIB 361 can be in astorage device internal or external to the NPU 359. The NPU 359 canimplement the FRR proxy functions described herein above as a proxyfunction module 363 and the switch functions described herein above as aswitch function module 365 that are executed as software, firmware orhardwired into the NPU 359. In other embodiments, the line cards 351A, Bcan include a separate central processing unit 355A (CPU), which is aprocessing device with general function and programmability that mayexecute the proxy function module 363 or switch function module 365.

In other embodiments, the proxy function module 363 and switch functionmodule 365 are implemented by the CPU 355B of the router, rather than aCPU 355A of a line card or set of line cards. The router CPU 355B canalso implement the discovery 371 and routing protocols that maintain therouting information base (RIB) 357. The RIB 357 can be maintained in astorage device internal or external to the CPU 355B. Similarly, the CPU355B can maintain or facilitate access to an event table 373 that mapsnetwork event identifiers to actions to be taken in response to thenetwork events.

It is to be understood that the above description is intended to beillustrative and not restrictive. Many other embodiments will beapparent to those of skill in the art upon reading and understanding theabove description. The scope of the invention should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

1. A method implemented by a router for executing an internet protocolfast reroute process in response to a network event invalidating acurrent route to a destination node without degrading forwarding planefunctionality or performance, the method comprising the steps of:receiving or generating the network event by the router, the networkevent associated with a network event identifier; looking up the networkevent identifier in an event table to determine routes that are affectedby the network event; determining whether a route with a fast rerouteforwarding object is affected by the network event in the routinginformation base; and overwriting a current next hop forwarding objectusing a backup next hop forwarding object in the forwarding informationbase.
 2. The method of claim 1, wherein the fast reroute forwardingobject is a fast reroute forwarding object including a replica primarynext hop forwarding object and a replica backup next hop forwardingobject.
 3. The method of claim 1, wherein overwriting the current nexthop forwarding object further comprises the step of: overwriting thecurrent next hop forwarding object in the forwarding information basewith the backup next hop forwarding object from the routing informationbase.
 4. The method of claim 1, wherein determining whether the routewith the fast reroute object is affected by the network event, furthercomprises the step of: determining whether the fast reroute object is ahierarchical fast reroute object.
 5. The method of claim 1, furthercomprising the step of: using a hierarchical fast reroute objectprepared before receipt of the network event by traversing a chain ofone or more non hierarchical fast reroute objects to generate acompressed primary next hop and one or more backup next-hops, where eachbackup next hop is associated with a network event.
 6. The method ofclaim 1, wherein determining whether a route with a fast rerouteforwarding object is affected by the network event in the routinginformation base further comprises the step of: determining whether aprimary route is valid after the network event.
 7. The method of claim1, wherein determining whether a route with a fast reroute forwardingobject is affected by the network event in the routing information basefurther comprises the step of: determining whether a backup route isvalid after the network event.
 8. A network element for executing aninternet protocol fast reroute process in response to a network eventinvalidating a current route to a destination node without degradingforwarding plane functionality or performance, the network elementcomprising: a first storage device to store a routing information base;a line card including a network processing device and a storage device,the storage device to store the forwarding information base, the networkprocessor configured to execute a proxy function module and a switchfunction module, the proxy function module configured to receive orgenerate the network event, the network event associated with a networkevent identifier, to look up the network event identifier in an eventtable to determine routes that are affected by the network event, and todetermine whether a route with a fast reroute forwarding object isaffected by the network event in the routing information base, and theswitch function module configured to overwrite a current next hopforwarding object using a backup next hop forwarding object in theforwarding information base.
 9. The network element of claim 8, whereinthe fast reroute forwarding object is a fast reroute forwarding objectincluding a replica primary next hop forwarding object and a replicabackup next hop forwarding object.
 10. The network element of claim 8,wherein the switching function module is further configured to overwritethe current next hop forwarding object in the forwarding informationbase with the backup next hop forwarding object from the routinginformation base.
 11. The network element of claim 8, wherein theswitching function module is further configured to determine whether thefast reroute object is a hierarchical fast reroute object.
 12. Thenetwork element of claim 8, wherein the proxy function module is furtherconfigured to traverse a chain of one or more non hierarchical fastreroute objects to generate a compressed primary next hop and one ormore backup next-hops, where each backup next hop is associated with anetwork event.
 13. The network element of claim 8, wherein the proxyfunction module is further configured to determine whether a primaryroute is valid after the network event.
 14. The network element of claim8, wherein the proxy function module is further configured to determinewhether a backup route is valid after the network event.